Method and apparatus for determining a physical location of a customer

ABSTRACT

A method and apparatus for determining a physical location of a customer of a network service, e.g., a Voice over Internet Protocol (VoIP) service are disclosed. For example, the method receives a Session Initiation Protocol (SIP) message containing a geographical coordinate data from a Customer Premise Equipment (CPE) device being used by a customer for accessing one or more services. The method retrieves the geographical coordinate data from the SIP message and provides the one or more services to the customer using the geographical coordinate data. In an alternate embodiment, a method and apparatus for sending physical location information are disclosed.

This application is a continuation of U.S. patent application Ser. No.11/781,567, filed Jul. 23, 2007, now U.S. Pat. No. 7,629,882, and hereinincorporated by reference in its entirety.

The present invention relates generally to communication networks and,more particularly, to a method for determining a physical location of acustomer of a network service, e.g., a Voice over Internet Protocol(VoIP) service.

BACKGROUND OF THE INVENTION

A network service provider may store a service address for a customer ina database when the customer initially subscribes to the service. Forexample, a VoIP service provider may store addresses of VoIP customersin a database. In order to ensure that customers of VoIP service areable to access emergency services, the Federal Communications Commission(FCC) mandates VoIP services to be provided only at a location whereE911 calls are supported (E911 services). For example, service providersmay restrict access to the VoIP service only to the known serviceaddress of a customer. For example, if a customer has a VoIP service athome, a VoIP operator may suspend the customer's access to the VoIPservice when he/she attempts to access the service from anotherlocation.

SUMMARY OF THE INVENTION

In one embodiment, the present invention discloses a method andapparatus for determining a physical location of a customer of a networkservice, e.g., a Voice over Internet Protocol (VoIP) service. Forexample, the method receives a Session Initiation Protocol (SIP) messagecontaining a geographical coordinate data from a Customer PremiseEquipment (CPE) device being used by a customer for accessing one ormore services. The method retrieves the geographical coordinate datafrom the SIP message and provides the one or more services to thecustomer using the geographical coordinate data.

In an alternate embodiment, the present invention discloses a method andapparatus for sending physical location information. For example, themethod determines geographical coordinate data for a Customer PremiseEquipment (CPE) device. The method then inserts the geographicalcoordinate data into a Session Initiation Protocol (SIP) message andforwards the SIP message to a service provider.

BRIEF DESCRIPTION OF THE DRAWINGS

The teaching of the present invention can be readily understood byconsidering the following detailed description in conjunction with theaccompanying drawings, in which:

FIG. 1 illustrates an exemplary network related to the presentinvention;

FIG. 2 illustrates an exemplary network with one embodiment of thepresent invention for determining the physical location of a customer;

FIG. 3 illustrates a flowchart of one embodiment of a method fordetermining the physical location of a customer;

FIG. 4 illustrates a flowchart of one embodiment of a method for sendingthe physical location information of a caller by a CPE device; and

FIG. 5 illustrates a high-level block diagram of a general-purposecomputer suitable for use in performing the functions described herein.

To facilitate understanding, identical reference numerals have beenused, where possible, to designate identical elements that are common tothe figures.

DETAILED DESCRIPTION

The present invention broadly discloses a method and apparatus fordetermining the physical location of a caller in a network, e.g., aVoice over Internet Protocol (VoIP) network. Although the presentinvention is discussed below in the context of VoIP services, thepresent invention is not so limited. Namely, the present invention canbe applied for any other services using Session Initiation Protocol(SIP) signaling.

To better understand the present invention, FIG. 1 illustrates anexample network, e.g., a packet network such as a VoIP network relatedto the present invention. Exemplary packet networks include Internetprotocol (IP) networks, Asynchronous Transfer Mode (ATM) networks,frame-relay networks, and the like. An IP network is broadly defined asa network that uses Internet Protocol to exchange data packets. Thus, aVoIP network or a SoIP (Service over Internet Protocol) network isconsidered an IP network.

In one embodiment, the VoIP network may comprise various types ofcustomer endpoint devices connected via various types of access networksto a carrier (e.g., a service provider) VoIP core infrastructure over anInternet Protocol/Multi-Protocol Label Switching (IP/MPLS) based corebackbone network. Broadly defined, a VoIP network is a network that iscapable of carrying voice signals as data packets over an IP network.The present invention is described below in the context of anillustrative VoIP network. Thus, the present invention should not beinterpreted as limited by this particular illustrative architecture.

The customer endpoint devices can be Time Division Multiplexing (TDM)based or IP based. For example, TDM based customer endpoint devices 122,123, 134, and 135 may comprise TDM phones or Private Branch Exchanges(PBXs). IP based customer endpoint devices 144 and 145 may comprise IPphones or IP PBXs. In one embodiment, the Terminal Adaptors (TA) 132 and133 are used to provide necessary inter-working functions between TDMcustomer endpoint devices, such as analog phones, and packet basedaccess network technologies, such as Digital Subscriber Loop (DSL) orCable broadband access networks. TDM based customer endpoint devices mayaccess VoIP services by using either a Public Switched Telephone Network(PSTN) 120, 121 or a broadband access network 130, 131 via the TA 132 or133. IP based customer endpoint devices may access VoIP services byusing either a Local Area Network (LAN) 140, 141 or a broadband accessnetwork 130 and 131. The LANs 140 and 141 may have VoIP gateway routers142 and 143, respectively.

The access networks can be either TDM or packet based. For example, aPSTN 120 or 121 is a TDM based access network used to support TDMcustomer endpoint devices connected via traditional phone lines. Apacket based access network, such as Frame Relay, ATM, Ethernet or IP,is used to support IP based customer endpoint devices via a customerLAN, e.g. LANs 140 and 141. A packet based broadband access network 130or 131, such as DSL or Cable, may be used to support IP devices such as144 and 145, as well as to support TDM based customer endpoint devicessuch as 134 and 135 when used with a TA 132 or 133.

The core VoIP infrastructure comprises of several key VoIP components,such as the Border Elements (BEs) 112 and 113, the Call Control Element(CCE) 111, VoIP related Application Servers (AS) 114, and Media Server(MS) 115. The BE resides at the edge of the VoIP core infrastructure andinterfaces with customers endpoints over various types of accessnetworks. A BE can be implemented as a Media Gateway and performssignaling, media control, security, and call admission control andrelated functions. The CCE resides within the VoIP infrastructure and isconnected to the BEs using the Session Initiation Protocol (SIP) overthe underlying IP/MPLS based core backbone network 110. The CCE can beimplemented as a Media Gateway Controller or a soft-switch and performsnetwork wide call control related functions as well as interacts withthe appropriate VoIP service related servers when necessary. The CCEfunctions as a SIP back-to-back user agent and is a signaling endpointfor all call legs between all BEs and the CCE. The CCE may need tointeract with various VoIP related Application Servers (AS) in order tocomplete a call that requires certain service specific features, e.g.,translation of an E.164 voice network address into an IP address and soon.

For calls that originate or terminate in a different carrier, they canbe handled through the PSTN 120 and 121 or the Partner IP Carrier 160interconnections. For originating or terminating TDM calls, they can behandled via existing PSTN interconnections to the other carrier. Fororiginating or terminating VoIP calls, they can be handled via thePartner IP carrier interface 160 to the other carrier.

In order to illustrate how the different components operate to support aVoIP call, the following call scenario is used to illustrate how a VoIPcall is setup between two customer endpoints. A customer using IP device144 at location A places a call to another customer at location Z usingTDM device 135. During the call setup, a setup signaling message is sentfrom IP device 144, through the LAN 140 and the VoIP Gateway/Router 142to BE 112. BE 112 will then send a setup signaling message, such as aSIP-INVITE message if SIP is used, to CCE 111. CCE 111 looks at thecalled party information and queries the necessary VoIP service relatedapplication server 114 to obtain the information to complete this call.In one embodiment, the Application Server (AS) functions as aback-to-back user agent. If BE 113 needs to be involved in completingthe call, CCE 111 sends another call setup message, such as a SIP-INVITEmessage if SIP is used, to BE 113. Upon receiving the call setupmessage, BE 113 forwards the call setup message, via broadband network131, to TA 133. TA 133 then identifies the appropriate TDM device 135and rings that device. Once the call is accepted at location Z by thecalled party, a call acknowledgement signaling message, such as a SIP200 OK response message if SIP is used, is sent in the reverse directionback to the CCE 111. After the CCE 111 receives the call acknowledgementmessage, it will then send a call acknowledgement signaling message,such as a SIP 200 OK response message if SIP is used, toward the callingparty. In addition, the CCE 111 also provides the necessary informationof the call to both BE 112 and BE 113 so that the call data exchange canproceed directly between BE 112 and BE 113. The call signaling path 150and the call media path 151 are illustratively shown in FIG. 1. Notethat the call signaling path and the call media path are differentbecause once a call has been setup between two endpoint devices, the CCE111 does not need to be in the data path for actual direct dataexchange.

Media Servers (MS) 115 are special servers that may handle and terminatemedia streams, and to provide services such as announcements, bridges,trans-coding, and Interactive Voice Response (IVR) messages for VoIPservice applications. The media servers may also interact with customersfor media session management to accomplish tasks such as processrequests.

Note that a customer in location A using any endpoint device type withits associated access network type can communicate with another customerin location Z using any endpoint device type with its associated networktype as well. For instance, a customer at location A using IP customerendpoint device 144 with packet based access network 140 can callanother customer at location Z using TDM endpoint device 123 with PSTNaccess network 121. The BEs 112 and 113 are responsible for thenecessary signaling protocol translation, e.g., SS7 to and from SIP, andmedia format conversion, such as TDM voice format to and from IP basedpacket voice format.

The above network is described to provide an illustrative environment inwhich packets are transported on networks, such as VoIP networks. When acustomer subscribes to a VoIP service, the service provider associatesthe request (service subscription) with the customer's telephone numberand device (e.g., a terminal adaptor or a router). For example, when acustomer initiates a VoIP session, the VoIP service provider associatesthe received request with the telephone number assigned to the customer.One of the concerns customers have about relying on the IP basedservices for all voice and data services is the fact that some servicesneed to be delivered based on the physical location of the user, but thecall may be originated from any location with an Internet access. Forexample, calls for emergency services, e.g., to a fire department, apolice station, etc. are intended to be received by a Public SafetyAnswering Point (PSAP) that serves the caller's present location. PSAPserving area boundaries are defined by local 911 authorities (e.g., cityand county governments, etc.). In order to clearly illustrate theteachings of the current invention, the following terminologies willfirst be described:

911 call;

911 tandem;

Public Safety Answering Point (PSAP); and

Enhanced 911 (E911).

A 911 call refers to a telephone call placed for the purpose ofrequesting emergency services. The public switched telephone network hasbeen enabled to recognize specific telephone numbers as a call foremergency services. The universal emergency telephone number used inNorth America is 911. The emergency call is delivered based ongeographical location of the caller to a public safety answering pointas defined below.

A 911 tandem refers to a switch that is used to connect telephoneswitching centers to the various public safety answering points. Forexample, when a wireless caller dials 911, the call is routed to amobile switching center. The mobile switching center is connected to the911 tandem that determines the public safety answering point that canbest service the call and then routes the call accordingly.

Public Safety Answering Point (PSAP) refers to a location whereemergency calls are received and distributed to the appropriateemergency service providers such as a fire department, a hospital, anambulance service dispatcher, a police dispatcher, etc. The servicesthat belong in a particular PSAP vary by community. The Incumbent LocalExchange Carrier (ILEC) manages the telephone equipment such as the 911tandem that routes the call to the appropriate public safety answeringpoint.

Enhanced 911 (E911) refers to an enhancement of technology that routesemergency calls (i.e., 911 calls) to the PSAP that has been designatedto serve the caller's location, and delivers the caller's call backnumber (Automatic Number Identification (ANI)) and location (AutomaticLocation Identification (ALI)).

Enhanced 911 calls can be delivered over a dedicated E911 network to aPublic Safety Answering Point (PSAP). In one embodiment, the dedicatedE911 network is contained within a traditional PSTN network. However, itshould be noted that a PSAP may support IP in the future. Generally, theemergency calls are delivered based on the geographical location of thecaller to the PSAP designated to serve that location. Regardless of thenetwork used to initiate the 911 call, the 911 calls will eventually besent to the proper PSAP.

In one embodiment, a VoIP service provider may store a service addressfor a VoIP customer in a database when the customer initially subscribesto the VoIP service and may provide a method for a PSAP to access thedatabase. For example, the VoIP service provider may store the addressin a database and provides an index that may be used to locate theaddress. When the customer initiates an emergency call, e.g., a 911call, from the service address, the VoIP service provider may identifythe caller, retrieve the caller's phone number, and forward the phonenumber to the 911 tandem that is located in the PSTN network. The VoIPservice provider may also send the index that may be used to locate thecustomer's service address. The local exchange carrier with the PSTNnetwork may then deliver the information from the 911 tandem to theproper PSAP. The call and the telephone number flow from the VoIPservice provider towards the PSAP. The PSAP may then use the index andthe phone number to retrieve the caller's address.

In order to ensure that customers of VoIP service are able to accessemergency services, the FCC mandates VoIP services to be provided onlyat a location where E911 calls are supported (E911 services). Forexample, service providers may restrict access to the VoIP service onlyto the known service address of a customer. For example, if a customerhas a VoIP service at home, a VoIP operator may suspend the customer'saccess to the VoIP service when he/she attempts to access the servicefrom another location.

In one embodiment, the current invention discloses a method andapparatus for determining a physical location of a customer of a networkservice, e.g., a VoIP service. The method first enables one or moreCustomer Premise Equipment (CPE) devices, e.g., TAs, routers, hubs, etc.to determine their own geographical location. For example, the CPEdevices may be equipped with the ability to determine satellite basedgeographical coordinate data, e.g., the United States' GlobalPositioning System (GPS), Europe's Galileo, Russia's Global NavigationSatellite System (GLONASS), and the like. The CPE device may theninclude the geographical coordinate data in a SIP message, as definedbelow. The accuracy of the geographical coordinate data may depend onthe particular satellite based system and the capabilities built intothe CPE devices. For example, a GPS system may provide a 3-dimensionalglobal positioning data accurate to within a few meters, e.g., within 3meters. As such, in one embodiment, a SIP message containing GPScoordinate data may then be used to determine a location within 3 metersof the CPE device (e.g., TA, router, hub) that a caller may be using.

A SIP message refers to a request from a client to a server or aresponse from a server to a client using the Session Initiation Protocol(SIP). In one embodiment, a SIP message contains a start line, one ormore header fields, an empty line indicating the end of the headerfields, and an optional message body. A SIP message is distinguished asa “request” when the start line is a request line. A request lineincludes a method name, a request Universal Resource Identifier (URI), aprotocol version, a single space character between the method name andURI, a single space character between the URI and protocol version, anda carriage return line feed. The method name may refer to any one of SIPmethods defined by standards organizations. Some illustrative examplesof SIP methods are:

-   -   REGISTER, used for registering contact information such as a        caller's current location (e.g., IP address and URI for server        close to the customer);    -   INVITE, used for inviting another caller to a conversation;    -   ACK, used for acknowledgements that facilitate reliable message        exchange between endpoints;    -   CANCEL, used to terminate a request or a search for a customer;    -   OPTIONS, used for soliciting information about a server's        capabilities;    -   INFO, used for mid-session signaling; and    -   BYE, used for terminating a connection between customers or for        declining a call.

For example, a SIP message for a request to register the contactinformation for a customer contains the method name “REGISTER” in thestart line. The request is also referred to as a “register request.” Aregister request may be sent by CPE devices to a special type of useragent server called a “registrar.” A register request can be sent insupport of a SIP discovery capability to enable sessions among callers.More specifically, the discovery capability refers to a process ofdetermining where to send session requests based on knowledge of thelocation of a customer (e.g., an intended destination IP address andtelephone number) and sending the request towards the destination. Inorder to perform discovery, SIP network elements may consult an abstractservice called a “location service.” The “location service” providesaddress bindings for a domain. The address bindings map an incoming SIPmessage to one or more Uniform Resource Identifiers (URIs) closest tothe desired destination. The location service provides the addressbindings based on data gathered when the customer registers to receiveservices via the registrar. Thus, in one embodiment, “registration”refers to a CPE device sending a register request to a registrar. Aregistrar operates as a front end server to the location service thatreceives register requests from the CPE devices, and places theinformation it receives in those requests into a location service forone or more domains it handles.

In one embodiment, the current invention enables a SIP registrar toreceive a SIP message containing a geographical coordinate data, e.g.,Global Positioning System (GPS) coordinate data, an IP address and/or atelephone number. In one embodiment, the geographical coordinate datamay be included as part of one or more SIP header fields. For example, aSIP header field may be modified to include the geographical coordinatedata. The CPE device may then populate the header field to include thegeographical coordinate data in addition to other header fields, e.g., aheader field containing an IP address. The SIP server may then retrievethe geographical coordinate data and IP address from the header fieldsin a register request, identify the caller, and retrieve the caller'sphone number.

In one embodiment, the geographical coordinate data may be included aspart of the message body. The message body is an optional part of a SIPmessage and may also be referred to as “payload.” The CPE device maythen provide the geographical coordinate data in the message bodyportion of a register request. The registrar may then read the messagebody portion of the register request and retrieves the geographicalcoordinate data for a customer.

The service provider may then use the geographical coordinate data toupdate the location information for the customer. For example, if thegeographical coordinate data is different from the location used in aprevious VoIP session, the service provider may update a LocationInformation Server (LIS) database for the customer. The updated LISdatabase may be utilized for providing services that are based onphysical location of the caller, e.g., E911 services. In this manner,the service provider may provide E911 service at the current physicallocation of the customer without disruption or suspension of the VoIPservice.

For example, if a VoIP customer accesses the VoIP service from a newlocation, the geographical coordinate data may be used to update an LISdatabase for the customer. If the customer initiates a 911 call, theVoIP service provider may then identify the caller from the IP address,retrieves the caller's phone number and geographical coordinate data,and forwards the phone number and GPS coordinate data to the 911 tandemthat is located in the PSTN network. The VoIP service provider may alsosend an index that may be used to locate the address corresponding tothe geographical coordinate data. The local exchange carrier with thePSTN network delivers the information from the 911 tandem to the properPSAP. The call, the telephone number, and the geographical coordinatedata or the index, flow from the VoIP service provider towards the PSAP.The PSAP may use either the geographical coordinate data or the indexthat may be used to locate the specific address corresponding to thegeographical coordinate data, and the phone number to retrieve thecaller's information for providing the emergency service.

FIG. 2 illustrates an exemplary network 200 with one embodiment of thepresent invention for determining the physical location of a customer.For example, a customer is using a TDM user endpoint device 134 toreceive a VoIP service by accessing an IP/MPLS core network 110 via anaccess network 130. In this example, the TDM user endpoint device 134 isconnected to the access network 130 via a TA 132. The access network 130is connected to the IP/MPLS core network 110 through a border element112. The IP/MPLS core network 110 contains a registrar 250, a locationdatabase 251, a location information server 252, and a VoIP applicationserver 114.

The IP/MPLS core network 110 is also connected to a PSTN access networkvia a border element 113. The PSTN network is capable of routing 911calls to a 911 tandem switch 210. In one embodiment, the 911-tandemswitch is connected to a plurality of Public Safety Answering Points(PSAPs) 220 a and 220 b. The 911 tandem switch forwards each 911 call tothe closest PSAP based on the physical location of the caller. Thepublic safety answering points 220 a and 220 b are, in turn, connectedto various emergency service providers 230, 231, 232 and 233. Eachcommunity will determine the emergency services such as the local policedepartment, ambulance service provider, fire department, and the like tobe connected to the PSAP. Thus, a caller using a user endpoint device134 is able to originate an emergency call that will be routed to aproper PSAP that will be able to service the emergency call.

In one embodiment, the TA 132 may determine its own GPS coordinate dataand may send SIP messages containing the GPS coordinate data. Forexample, when a customer initiates a VoIP session, the TA 132 may sendone or more register requests containing the GPS coordinate data.

In one embodiment, the VoIP service provider enables a customer toaccess the VoIP application server 114 and to subscribe to a VoIPservice. The VoIP service provider may record the IP addresses and GPScoordinate data (or addresses corresponding to GPS coordinate data) ofcustomer endpoint devices in the location database 251. For example, theregistrar 250 may retrieve the GPS coordinate data from a registerrequest and records the GPS coordinate data in the location database251. For example, if the CPE device 134 sends a SIP register request tothe registrar 250 (via the TA 132 and the access network 130), theregistrar 250 reads the GPS coordinate data provided by the TA 132 anddetermines whether or not the received GPS coordinate data is differentfrom the GPS coordinate data for the customer from the previous session.For example, the received GPS coordinate data may be compared to thatretrieved from the location database 251. If the received GPS coordinatedata is different from the GPS coordinate data from the previoussession, the method then updates the GPS coordinate data for thecustomer in the location database 251 and the LIS 252. The serviceprovider is then able to provide the VoIP service to the customer at thecurrent physical location, even if the current physical location isdifferent from a service location that is associated with the customer.

In one embodiment, the user endpoint device may be equipped with thecapability to determine its own geographical coordinate data. Forexample, a telephone may be equipped with GPS capability. When acustomer accesses the VoIP service with such capability, the CPE mayreceive the geographical coordinate data from the user endpoint deviceand forward the received geographical coordinate data in the SIPmessage. For example, the CPE may determine that the geographicalcoordinate data received from a user endpoint device is not identical toits own geographical coordinate data. The CPE may then transmit thereceived geographical coordinate data instead of its own.

In another embodiment, the CPE may send both its own geographicalcoordinate data and that of the user endpoint device. For example, a CPEmay be shared by several user endpoint devices and it may be importantto determine the specific location of the user when an emergency call isoriginated via the CPE. For example, a hotel may have several rooms allsharing a router. When a VoIP customer accesses from a specific room ina hotel, it may be necessary to know the location of the customer aswell as the location of the router. For example, the router's locationmay be used in an index to determine the street address of the hotel,while the location of the user endpoint device may be used in a separateindex (as a secondary parameter) to locate the caller.

In one embodiment, the CPE may be configured with a threshold forsending the geographical coordinate data of a user endpoint device. Forexample, if the user endpoint device is within 10 meters of the CPEdevice, it may not be useful or necessary to transmit the geographicalcoordinate data of the user endpoint device.

However, in another example, a customer may dial 911 while walkingaround his/her neighborhood. In that case, the geographical coordinatedata of the user endpoint device may be used to deliver emergencyservices to the physical location of the caller instead of the locationof the router or TA, which will likely be in the home of the customer.

FIG. 3 illustrates a flowchart of one embodiment of a method 300 fordetermining the physical location of a customer. Method 300 starts instep 305 and proceeds to step 310.

In step 310, method 300 receives a SIP message containing a geographicalcoordinate data from a Customer Premise Equipment (CPE) device. Forexample, a SIP registrar receives a SIP message containing a GlobalPositioning System (GPS) coordinate data, an IP address and/or atelephone number.

In step 320, method 300 retrieves the geographical coordinate data fromthe SIP message. For example, the SIP registrar may retrieve thegeographical coordinate data and IP address from one or more headerfields in a register request.

In one alternate embodiment, the geographical coordinate data isreceived as part of the message body portion of the SIP message. Theregistrar may then read the message body portion of the register requestand obtains the geographical coordinate data for a customer.

In step 330, method 300 updates the location information for thecustomer in accordance with the geographical coordinate data. Forexample, the method may use the geographical coordinate data to updatethe location information for the customer stored in a LocationInformation Server (LIS) database.

In step 340, method 300 provides a service, e.g., a VoIP service, to thecustomer using the location information. The method then proceeds backto step 310 to continue receiving SIP messages.

In one embodiment, the method may compare the geographical coordinatedata with the geographical coordinate data used by the customer in thelast session prior to the current session and performs an update only ifthe newly received geographical coordinate data is different.

FIG. 4 illustrates a flowchart of one embodiment of a method 400 forsending the physical location information of a customer by a CPE device.Method 400 starts in step 405 and proceeds to step 410.

In step 410, method 400 determines one or more geographical coordinatedata. For example, a CPE device may be able to determine its own GPScoordinate data, e.g., using GPS receivers employed in the CPE device.Furthermore, the CPE device may optionally receive geographicalcoordinate data from a user endpoint device, e.g., via a SIP registerrequest from a user endpoint device that the CPE device services. Thus,method 400 is able to determine geographical coordinate data of the CPEdevice and/or the geographical coordinate data of the user endpointdevice.

In step 420, method 400 embeds the one or more geographical coordinatedata in a SIP message. For example, the geographical coordinate data ofthe CPE device can be inserted into a SIP message. Alternatively, if thegeographical coordinate data of the user endpoint device is alreadypresent in a SIP message, then the CPE device may then modify the SIPmessage to include its own geographical location. In one embodiment, thegeographical coordinate data is included as part of the SIP headerfields. For example, the SIP header fields may be modified to includethe geographical coordinate data. Namely, the CPE device may populatethe header field(s) to include the geographical coordinate data inaddition to other header fields, e.g., IP address and the like. In analternate embodiment, the geographical coordinate data is included inthe SIP message as part of the message body.

In one embodiment, the geographical coordinate data is a geographicalcoordinate data determined by a user endpoint device and forwarded tothe CPE device. For example, a user endpoint device may determine itsown location via GPS receivers and sends the data to the CPE device. TheCPE device may then optionally use the geographical coordinate datareceived from the user endpoint device in conjunction with, or insteadof its own geographical coordinate data.

In one embodiment, the CPE may be configured with a threshold forreplacing its own geographical coordinate data with the geographicalcoordinate data of a user endpoint device. For example, the CPE deviceis able to determine or calculate a difference between the geographicalcoordinate data of the user endpoint device and the geographicalcoordinate data of the CPE. The CPE device may use the geographicalcoordinate data of the user endpoint device if the calculated differencein geographical coordinate data exceeds the predefined threshold. Forexample, if the CPE device determines that the user endpoint device isgreater than 50 meters in distance from the CPE device, then thegeographical coordinate data of the user endpoint device will beinserted into the SIP message instead of the geographical coordinatedata of the CPE. One rationale is that since the user endpoint device isat a significant distance from the CPE device, it may be more importantthat the geographical coordinate data of the user endpoint device bemade known to the service provider in the event that emergency serviceis to be provided to the customer.

In another embodiment, the CPE may include both its own geographicalcoordinate data and that of the user endpoint device in a SIP message.For example, there may be more than one header field for geographicalcoordinate data thereby enabling the CPE to insert both its owngeographical coordinate data and that of the user endpoint device intothe SIP message. One rationale is that although the user endpoint deviceis not at a significant distance from the CPE device, it may still beimportant that the geographical coordinate data of the user endpointdevice be made known to the service provider in the event that emergencyservice is to be provided to the customer.

In one alternate embodiment, the CPE device may ignore the geographicalcoordinate data of the user endpoint device. For example, if the CPEdevice determines that the user endpoint device is less than 5 meters indistance from the CPE device, then the geographical coordinate data ofthe user endpoint device will not be inserted into the SIP message.Instead only the geographical coordinate data of the CPE is inserted inthe SIP message. One rationale is that since the user endpoint device isat an insignificant distance from the CPE device, it is not importantthat the geographical coordinate data of the user endpoint device bemade known to the service provider in the event that emergency serviceis to be provided to the customer.

In step 430, method 400 forwards the SIP message containing one or moregeographical coordinate data towards a network server, e.g., theregister server. The method then returns to step 410.

It should be noted that although not specifically specified, one or moresteps of methods 300 and 400 may include a storing, displaying and/oroutputting step as required for a particular application. In otherwords, any data, records, fields, and/or intermediate results discussedin the method can be stored, displayed and/or outputted to anotherdevice as required for a particular application. Furthermore, steps orblocks in FIG. 3 and FIG. 4 that recite a determining operation orinvolve a decision, do not necessarily require that both branches of thedetermining operation be practiced. In other words, one of the branchesof the determining operation can be deemed as an optional step.

FIG. 5 depicts a high-level block diagram of a general-purpose computersuitable for use in performing the functions described herein. Asdepicted in FIG. 5, the system 500 comprises a processor element 502(e.g., a CPU), a memory 504, e.g., random access memory (RAM) and/orread only memory (ROM), a module 505 for determining the physicallocation of a customer or for sending physical location information of acaller, and various input/output devices 506 (e.g., storage devices,including but not limited to, a tape drive, a floppy drive, a hard diskdrive or a compact disk drive, a receiver, a transmitter, a speaker, adisplay, a speech synthesizer, an output port, and a user input device(such as a keyboard, a keypad, a mouse, alarm interfaces, power relaysand the like)).

It should be noted that the present invention can be implemented insoftware and/or in a combination of software and hardware, e.g., usingapplication specific integrated circuits (ASIC), a general-purposecomputer or any other hardware equivalents. In one embodiment, thepresent module or process 505 for determining the physical location of acustomer or for sending physical location information of a caller can beloaded into memory 504 and executed by processor 502 to implement thefunctions as discussed above. As such, the present method 505 fordetermining the physical location of a customer or for sending physicallocation information of a caller (including associated data structures)of the present invention can be stored on a computer readable medium orcarrier, e.g., RAM memory, magnetic or optical drive or diskette and thelike.

While various embodiments have been described above, it should beunderstood that they have been presented by way of example only, and notlimitation. Thus, the breadth and scope of a preferred embodiment shouldnot be limited by any of the above-described exemplary embodiments, butshould be defined only in accordance with the following claims and theirequivalents.

1. A method for determining a physical location of a customer,comprising: receiving a signaling message containing geographicalcoordinate data from a customer premise equipment device being used by acustomer for accessing a service; retrieving the geographical coordinatedata from the signaling message; and providing the service to thecustomer using the geographical coordinate data.
 2. The method of claim1, wherein the geographical coordinate data comprises satellite basedgeographical coordinate data.
 3. The method of claim 1, wherein thegeographical coordinate data is retrieved from a header field in thesignaling message.
 4. The method of claim 1, wherein the geographicalcoordinate data is retrieved from a message body portion of thesignaling message.
 5. The method of claim 1, further comprising:updating physical location information for the customer in accordancewith the geographical coordinate data.
 6. The method of claim 5, whereinthe updating the physical location information for the customercomprises: determining whether the geographical coordinate data is thesame as previous geographical coordinate data for the customer; andupdating a database of a location information server for the customer ifthe geographical coordinate data of the customer is not the same as theprevious geographical coordinate data for the customer.
 7. The method ofclaim 1, wherein the geographical coordinate data is that of thecustomer premise equipment device.
 8. The method of claim 1, wherein thegeographical coordinate data is that of a user endpoint device accessingthe service via the customer premise equipment device.
 9. The method ofclaim 1, wherein the geographical coordinate data comprises geographicalcoordinate data of the customer premise equipment device andgeographical coordinate data of a user endpoint device accessing theservice via the customer premise equipment device.
 10. The method ofclaim 1, wherein the signaling message is received during a registrationprocess.
 11. A computer-readable medium having stored thereon aplurality of instructions, the plurality of instructions includinginstructions which, when executed by a processor, cause the processor toperform a method for determining a physical location of a customer,comprising: receiving a signaling message containing geographicalcoordinate data from a customer premise equipment device being used by acustomer for accessing a service; retrieving the geographical coordinatedata from the signaling message; and providing the service to thecustomer using the geographical coordinate data.
 12. Thecomputer-readable medium of claim 11, wherein the geographicalcoordinate data comprises satellite based geographical coordinate data.13. The computer-readable medium of claim 11, wherein the geographicalcoordinate data is retrieved from a header field in the signalingmessage.
 14. The computer-readable medium of claim 11, wherein thegeographical coordinate data is retrieved from a message body portion ofthe signaling message.
 15. The computer-readable medium of claim 11,further comprising: updating physical location information for thecustomer in accordance with the geographical coordinate data.
 16. Thecomputer-readable medium of claim 11, wherein the updating the physicallocation information for the customer comprises: determining whether thegeographical coordinate data is the same as previous geographicalcoordinate data for the customer; and updating a database of a locationinformation server for the customer if the geographical coordinate dataof the customer is not the same as the previous geographical coordinatedata for the customer.
 17. The computer-readable medium of claim 11,wherein said the geographical coordinate data is that of the customerpremise equipment device.
 18. The computer-readable medium of claim 11,wherein the geographical coordinate data is that of a user endpointdevice accessing the service via the customer premise equipment device.19. The computer-readable medium of claim 11, wherein the geographicalcoordinate data comprises geographical coordinate data of the customerpremise equipment device and geographical coordinate data of a userendpoint device accessing the service via the customer premise equipmentdevice.
 20. A method for sending physical location information,comprising: determining geographical coordinate data for a customerpremise equipment device; inserting the geographical coordinate datainto a signaling message; and forwarding the signaling message to aservice provider.